According to @deanmlittle, Anchor PR #4060 spotlights severe limitations in Solana program upgrade tooling, amplifying @jarxiao’s call for safer, system-level mechanisms. source: X/@deanmlittle 2025-12-30 https://twitter.com/deanmlittle/status/2005887153461719130; GitHub solana-foundation/anchor PR #4060 https://github.com/solana-foundation/anchor/pull/4060; X/@jarxiao thread https://x.com/jarxiao/status/2005783134910996513. Solana program data schemas are effectively locked post-deployment, making safe upgrades difficult and brittle for complex contracts. source: X/@jarxiao thread https://x.com/jarxiao/status/2005783134910996513. Common workarounds such as struct padding, user-signed state migrations, or app-level admin actions introduce logical data risk, key-management risk, and can break VM-level composability. source: X/@jarxiao thread https://x.com/jarxiao/status/2005783134910996513. Proposed fixes include separate VM APIs for reading and writing account data, opt-in system-level administrative functions, and optional atomic migrations of program-owned accounts on executable upgrade. source: X/@jarxiao thread https://x.com/jarxiao/status/2005783134910996513; GitHub solana-foundation/anchor PR #4060 https://github.com/solana-foundation/anchor/pull/4060. For traders, this highlights upgrade-related operational risk in Solana dApps and a clear roadmap to watch via Anchor PR #4060 and any adoption of system-level tooling across the SOL ecosystem. source: X/@jarxiao thread https://x.com/jarxiao/status/2005783134910996513; GitHub solana-foundation/anchor PR #4060 https://github.com/solana-foundation/anchor/pull/4060; X/@deanmlittle 2025-12-30 https://twitter.com/deanmlittle/status/2005887153461719130.